<!-- HTML header for doxygen 1.8.3.1-->
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head>
<meta http-equiv="Content-Type" content="text/xhtml;charset=UTF-8"/>
<meta http-equiv="X-UA-Compatible" content="IE=9"/>
<meta name="generator" content="Doxygen 1.8.13"/>
<title>Nordic Thingy:52 v2.2.0 : Release Notes</title>
<link href="tabs.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="jquery.js"></script>
<script type="text/javascript" src="dynsections.js"></script>
<link href="navtree.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="resize.js"></script>
<script type="text/javascript" src="navtreedata.js"></script>
<script type="text/javascript" src="navtree.js"></script>
<script type="text/javascript">
  $(document).ready(initResizable);
</script>
<link href="search/search.css" rel="stylesheet" type="text/css"/>
<script type="text/javascript" src="search/searchdata.js"></script>
<script type="text/javascript" src="search/search.js"></script>
<link href="doxygen.css" rel="stylesheet" type="text/css" />
<link href="extra_stylesheet_offline.css" rel="stylesheet" type="text/css"/>
<link href="nordic.css" rel="stylesheet" type="text/css" />
</head>
<body>
<div id="top"><!-- do not remove this div, it is closed by doxygen! -->
<div id="titlearea">
<table cellspacing="0" cellpadding="0" width="100%" class="blank">
 <tbody>
 <tr style="height: 56px;">
  <td id="projectlogo"><img alt="Nordic Semiconductor" src="nordic_small.png"/></td>
  <td style="padding-left: 0.5em;">
   <div id="projectname">Nordic Thingy:52 v2.2.0
   </div>
  </td>
 </tr>
 </tbody>
</table>
<script>
var url=window.location.href.split("/").reverse()[1];
var validLinks= ["nrf5","s130","s132","s212","s332"];
var index;
for (index = 0; index < validLinks.length; ++index) {
   if ( url.indexOf(validLinks[index]) !== -1 ) {
      document.getElementById(validLinks[index]).setAttribute('class', 'doclinks docselected');
   };
};
</script>
</div>
<!-- end header part -->
<!-- Generated by Doxygen 1.8.13 -->
<script type="text/javascript">
var searchBox = new SearchBox("searchBox", "search",false,'Search');
</script>
<script type="text/javascript" src="menudata.js"></script>
<script type="text/javascript" src="menu.js"></script>
<script type="text/javascript">
$(function() {
  initMenu('',true,false,'search.php','Search');
  $(document).ready(function() { init_search(); });
});
</script>
<div id="main-nav"></div>
</div><!-- top -->
<div id="side-nav" class="ui-resizable side-nav-resizable">
  <div id="nav-tree">
    <div id="nav-tree-contents">
      <div id="nav-sync" class="sync"></div>
    </div>
  </div>
  <div id="splitbar" style="-moz-user-select:none;" 
       class="ui-resizable-handle">
  </div>
</div>
<script type="text/javascript">
$(document).ready(function(){initNavTree('release_notes.html','');});
</script>
<div id="doc-content">
<!-- window showing the filter options -->
<div id="MSearchSelectWindow"
     onmouseover="return searchBox.OnSearchSelectShow()"
     onmouseout="return searchBox.OnSearchSelectHide()"
     onkeydown="return searchBox.OnSearchSelectKey(event)">
</div>

<!-- iframe showing the search results (closed by default) -->
<div id="MSearchResultsWindow">
<iframe src="javascript:void(0)" frameborder="0" 
        name="MSearchResults" id="MSearchResults">
</iframe>
</div>

<div class="header">
  <div class="headertitle">
<div class="title">Release Notes </div>  </div>
</div><!--header-->
<div class="contents">
<div class="textblock"><h2>Nordic Thingy:52 firmware version 2.2.0</h2>
<p><b>Built on nRF5 SDK v13.0.0</b></p>
<p><b>Uses SoftDevice S132 v4.0.2</b></p>
<p>Tested with the following versions of GCC and Keil:</p><ul>
<li>gcc_arm_none_eabi 4.9 2015q3</li>
<li>Keil version 5.26</li>
</ul>
<h3>New features</h3>
<ul>
<li>The content of the NFC tag is now configurable over BLE.</li>
</ul>
<h3>Changes</h3>
<ul>
<li>The Thingy Configuration Service has been expanded with an additional characteristic for adding data to the NFC tag. Note that the data is not parsed, and the maximum length of the data is set by the MTU size, to a maximum of 247.</li>
</ul>
<h3>Known issues</h3>
<ul>
<li>Due to the strong magnetic interference by the speaker, compass accuracy is limited.</li>
<li>Thingy gas sensor requires 48 hours of operation time (burn in) to self-calibrate.</li>
<li>If you compile a debug version of the firmware, error logs in the RTT console when a function returns an error code, even when the error is correctly handled by the firmware.</li>
<li>Speaker status notifications may arrive out of order under load.</li>
<li>Writing the device name characteristic may sometimes fail to update the device name field in advertising packets.</li>
<li>Performing extensive enabling/disabling of sensors might reboot Thingy.</li>
<li>Configuring very optimistic service intervals may cause Thingy to reboot. Examples:<ul>
<li>Sound streaming and motion sensor simultaneously.</li>
<li>Motion sensor and several environment sensors configured for lowest notification interval.</li>
</ul>
</li>
<li>Sound service streaming will not work on older mobile devices due to low bandwidth.</li>
<li>The first 10 seconds of motion sensor data may be inaccurate due to calibration.</li>
<li>Preproduction versions of the Thingy hardware will not be able to perform OTA-DFU of the bootloader.</li>
<li>Quaternion will always start at identity when turning the service on (Enabling quaternion notifications will always start at Identity (0,0,0,1), equivalent of Eulers (0,0,0)).</li>
</ul>
<dl class="section note"><dt>Note</dt><dd>The micro-ecc library is used in the Thingy bootloader. See <a href="./license.txt" target="_blank">license.txt</a> for the license of this library.</dd></dl>
<h2>Nordic Thingy:52 firmware version 2.1.0</h2>
<p><b>Built on nRF5 SDK v13.0.0</b></p>
<p><b>Uses SoftDevice S132 v4.0.2</b></p>
<p>Tested with the following versions of GCC and Keil:</p><ul>
<li>gcc_arm_none_eabi 4.9 2015q3</li>
<li>Keil version 5.20</li>
</ul>
<h3>New features</h3>
<ul>
<li>Thingy now reports remaining battery charge (state of charge - "SoC") based on experiments and models.</li>
</ul>
<h3>Changes</h3>
<ul>
<li>The full charge definition has been altered from 4.150 V to 4.190 V to better correspond with the new battery model. Note that Thingy may not always reach 100 % charge.</li>
</ul>
<h3>Bugfixes</h3>
<ul>
<li>The battery charge monitor did not report actual values in 2.0.0. This has been corrected.</li>
</ul>
<h3>Known issues</h3>
<ul>
<li>Due to the strong magnetic interference by the speaker, compass accuracy is limited.</li>
<li>Thingy gas sensor requires 48 hours of operation time (burn in) to self-calibrate.</li>
<li>If you compile a debug version of the firmware, error logs in the RTT console when a function returns an error code, even when the error is correctly handled by the firmware.</li>
<li>Speaker status notifications may arrive out of order under load.</li>
<li>Writing the device name characteristic may sometimes fail to update the device name field in advertising packets.</li>
<li>Performing extensive enabling/disabling of sensors might reboot Thingy.</li>
<li>Configuring very optimistic service intervals may cause Thingy to reboot. Examples:<ul>
<li>Sound streaming and motion sensor simultaneously.</li>
<li>Motion sensor and several environment sensors configured for lowest notification interval.</li>
</ul>
</li>
<li>Sound service streaming will not work on older mobile devices due to low bandwidth.</li>
<li>The first 10 seconds of motion sensor data may be inaccurate due to calibration.</li>
<li>Preproduction versions of the Thingy hardware will not be able to perform OTA-DFU of the bootloader.</li>
<li>Quaternion will always start at identity when turning the service on (Enabling quaternion notifications will always start at Identity (0,0,0,1), equivalent of Eulers (0,0,0)).</li>
</ul>
<dl class="section note"><dt>Note</dt><dd>The micro-ecc library is used in the Thingy bootloader. See <a href="./license.txt" target="_blank">license.txt</a> for the license of this library.</dd></dl>
<h2>Nordic Thingy:52 firmware version 2.0.0</h2>
<p><b>Built on nRF5 SDK v13.0.0</b></p>
<p><b>Uses SoftDevice S132 v4.0.2</b></p>
<p>Tested with the following versions of GCC and Keil:</p><ul>
<li>gcc_arm_none_eabi 4.9 2015q3</li>
<li>Keil version 5.20</li>
</ul>
<h3>New features</h3>
<ul>
<li>NFC functionality has been added. The NFC tag contains records of the mobile app on Android for automatic app launch, a link to Thingy:52 webpages and a string containing the MAC address, as well as a random generated address. The latter 4-byte ID is randomly generated on each boot and displayed in the BLE advertise response packet as well.</li>
</ul>
<h3>Changes</h3>
<ul>
<li>The upper BLE notification limit has been increased to 60 seconds for temperature, pressure, humidity, and color to improve compatibility with IoT needs.</li>
<li>The lower delay limit for LED breathe has been increased from 1 ms to 50 ms.</li>
<li>The minimum motion processing frequency set to 5 Hz.</li>
<li>Upon BLE connection, the lightwell used to change to a cyan color. This has been changed to green.</li>
<li>The entire project has been converted to NRF_LOG for Real Time Terminal (RTT) output.</li>
<li>When requesting a new LED breathe command, all counters of the IO extender will be restarted. This ensures better LED response, but will reset the light cycle of any connected LED.</li>
</ul>
<h3>Bugfixes</h3>
<ul>
<li>The compass has been integrated in the motion processing and Thingy will indicate magnetic North. Rotate Thingy around the Z axis back an forth to get compass lock.</li>
</ul>
<h3>Known issues</h3>
<ul>
<li>Due to the strong magnetic interference by the speaker, compass accuracy is limited.</li>
<li>Thingy gas sensor requires 48 hours of operation time (burn in) to self-calibrate.</li>
<li>If you compile a debug version of the firmware, error logs in the RTT console when a function returns an error code, even when the error is correctly handled by the firmware.</li>
<li>Speaker status notifications may arrive out of order under load.</li>
<li>Writing the device name characteristic may sometimes fail to update the device name field in advertising packets.</li>
<li>Performing extensive enabling/disabling of sensors might reboot Thingy.</li>
<li>Configuring very optimistic service intervals may cause Thingy to reboot. Examples:<ul>
<li>Sound streaming and motion sensor simultaneously.</li>
<li>Motion sensor and several environment sensors configured for lowest notification interval.</li>
</ul>
</li>
<li>Sound service streaming will not work on older devices due to low bandwidth.</li>
<li>The first 10 seconds of motion sensor data may be inaccurate due to calibration.</li>
<li>Preproduction versions of the Thingy hardware will not be able to perform OTA-DFU of the bootloader.</li>
<li>Quaternion will always start at identity when turning the service on (Enabling quaternion notifications will always start at Identity (0,0,0,1), equivalent of Eulers (0,0,0)).</li>
</ul>
<dl class="section note"><dt>Note</dt><dd>The micro-ecc library is used in the Thingy bootloader. See <a href="./license.txt" target="_blank">license.txt</a> for the license of this library.</dd></dl>
<h2>Nordic Thingy:52 firmware version 1.1.0</h2>
<p><b>Built on nRF5 SDK v12.1.0</b></p>
<p><b>Uses SoftDevice S132 v3.0.0</b></p>
<p>Tested with the following versions of GCC and Keil:</p><ul>
<li>gcc_arm_none_eabi 4.9 2015q3</li>
<li>Keil version 5.20</li>
</ul>
<h3>Known issues</h3>
<ul>
<li>Compass heading values are reversed, when rotating the Thingy clockwise the heading data decreases.</li>
<li>RGB LED configurations might get out of sync for one breathe cycle.</li>
<li>The Thingy gas sensor reqires 48 hours of operation time (burn in) to self-calibrate.</li>
<li>Error logs in the RTT console when a function returns an error code, even when the error is correctly handled by the firmware.</li>
<li>The scenario of running OTA-DFU on an application that would extend into the FDS data area is not tested.</li>
<li>Speaker status notifications may arrive out of order under load.</li>
<li>Speaker status notifications may be lost when switching between speaker modes.</li>
<li>Writing the device name characteristic may sometimes fail to update the device name field in advertising packets.</li>
<li>Performing extensive enabling/disabling of sensors might reboot the Thingy.</li>
<li>Configuring very optimistic service intervals may cause the Thingy to reboot. Examples:<ul>
<li>Sound streaming and motion sensor simultaneously.</li>
<li>Motion sensor and several environment sensors configured for lowest notification interval.</li>
</ul>
</li>
<li>Color sensor is not calibrated for the blue color in the base plastic casing. This issue will be fixed in a firmware update.</li>
<li>Sound service streaming will not work on older devices due to low bandwidth.</li>
<li>The first 10 seconds of motion sensor data may be inaccurate due to calibration.</li>
<li>When motion data frequency is set below 5 Hz, the data becomes invalid.</li>
<li>Preproduction versions of the Thingy hardware will not be able to perform OTA-DFU of the bootloader.</li>
<li>Quaternion will always start at identity when turning the service on (Enabling quaternion notifications will always start at Identity (0,0,0,1), equivalent of Eulers (0,0,0)).</li>
<li>When activated, the compass module uses its present heading as North. The heading is given relatively to this initial setting, and the value increases counterclockwise.</li>
</ul>
<dl class="section note"><dt>Note</dt><dd>The micro-ecc library is used in the Thingy bootloader. See <a href="./license.txt" target="_blank">license.txt</a> for the license of this library. </dd></dl>
</div></div><!-- contents -->
</div><!-- doc-content -->
<div id="nav-path" class="topicfooter">
<a href="mailto:docfeedback@nordicsemi.no?subject=Documentation%20feedback" id="maillink">Documentation feedback</a> | <a href="https://devzone.nordicsemi.com/questions/" target="_blank">Developer Zone</a> | <a href="http://response.nordicsemi.com/subscribe-to-our-newsletters" target="_blank">Subscribe</a> | Updated <span id="date"/>
<script>
var date = new Date("Thu Feb 7 2019" + " UTC");
document.getElementById("date").innerHTML = date.toJSON().slice(0, 10);
var url=window.location.href.split("?")[0];
var filename=url.substring(url.lastIndexOf('/')+1);
document.getElementById("maillink").href = "mailto:docfeedback@nordicsemi.no?subject=Documentation%20feedback"+decodeURIComponent("%26")+"body=File%20name%3A%20"+encodeURIComponent(filename);
</script>
</div>
</body>
</html>
